* Core infrastructure for terraform 19 added

* Updated README and fixes

* Added BYO support for terraform 19

* Clean ups for terraform 19

* Added support for private ACR

* Added tools tests for terraform 19

* Renamed Template

* Address Comments

* Address Comments

…ates (11, 15, 16, 17, 19) (#560)

* fix(private-network-agent-tools): Avoid duplicate privatelink.azurecr.io vnet link

* feat: Add App Insights + AMPLS tracing to private-network agent templates

* docs: Document App Insights + AMPLS tracing in private-network template READMEs

* feat: Add Application Insights + AMPLS tracing to private-network Terraform templates

* feat(bicep): support BYO/centralized Private DNS Zones for AMPLS tracing

The new Azure Monitor Private Link Scope module always created and VNet-linked
the four Azure Monitor private DNS zones. In an Azure Landing Zone with
centralized Private DNS Zones (zones owned in a connectivity subscription and
records registered by policy), this produces duplicate workload-local zones and
a competing VNet link - the same class of conflict the duplicate azurecr.io link
fix in this PR addressed.

Extend monitor-private-link-scope.bicep with an existingDnsZones map (zone name
-> resource group; empty means create) and a dnsZonesSubscriptionId parameter,
mirroring the existing private-endpoint-and-dns.bicep / container-registry.bicep
BYO pattern. Zones and VNet links are now created only when not supplied; BYO
zones are referenced (optionally cross-subscription) in the private DNS zone
group instead of recreated. Wired through each template's main.bicep via a new
existingMonitorDnsZones parameter (templates 11/15/16/17/19).

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* fix(terraform): Correct 15a deleted account purge resource type

* revert(terraform): Remove tracing from TF16 and TF17

Both samples are missing hosted-agent network injection in addition to the gaps documented in their READMEs, so the tracing changes cannot be validated end-to-end.

* fix(bicep): Use per-zone DNS settings for template 19 AMPLS zones

---------

Co-authored-by: Haflidi Fridthjofsson <26624010+haflidif@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Adding LangGraph A2A sample

* Update LangGraph A2A sample to A2A protocol v1.0

* Exclude LangGraph A2A caller from hosted-agents e2e CI (multi-agent, can't deploy standalone)

…azd recommendations (#585)

* docs(hosted-agents): collapse Foundry Toolkit section and neutralize azd recs

Minimal README updates across the python and csharp hosted-agents samples: collapse the 'Using the Foundry Toolkit VS Code Extension' section into a <details> block, drop azd 'Recommended'/'recommended' qualifiers, and rename 'Without azd' to 'Manual setup' (with anchor fixes). H1 headers, descriptions, and other section content are left unchanged.

* docs(hosted-agents): revert Python overview README